| focus() | Building Object Hierarchies | |
This Knowledge Representation is an option available in some Editions of XpertRule Knowledge Builder
Hierarchy Objects enable you to define structures showing peer-child relationship of Objects. For example, in a configuration application it could be used to define a "Bill of Materials" structure of subassembly components that make-up a configurable product. In a contract document generation application, it could be used to represent the contract structure - where components in this case represent clauses and sub-clauses of the document (see the sections on Building Configuration Applications and Accessing the Runtime Hierarchy Data).
You can have one or several Object Hierarchies in an application. Note that where components have sub components (e.g. in the case of subassemblies), that the structure you see in the hierarchy editor is tied directly to the subassembly itself - that is, to the object in the Knowledge Explorer. This means that if you change a subassembly's structure within one Object Hierarchy that the changes will be reflected in ALL the other Hierarchies where it is used.
Typically, Hierarchies can be invoked from the Main Agenda or Procedure
@Do <hierarchy_name>
Note that hierarchy is a reserved word within Knowledge Builder Scripting.